Skip to content

Conversation

@jsanz
Copy link
Member

@jsanz jsanz commented Nov 26, 2025

Follow up from #516

In order to get glob to a non vulnerable version, we need to move from a direct dependency to a resolution, so all dependencies also resolve to the same, non-vulnerable version of the library.

@prodsecmachine
Copy link

prodsecmachine commented Nov 26, 2025

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@jsanz jsanz added the dependencies Pull requests that update a dependency file label Nov 26, 2025
@jsanz jsanz requested a review from nickpeihl November 26, 2025 15:42
@jsanz jsanz marked this pull request as ready for review November 26, 2025 15:42
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

@jsanz jsanz merged commit da8c4b2 into elastic:master Nov 26, 2025
5 checks passed
@jsanz jsanz deleted the update/glob branch November 26, 2025 16:21
github-actions bot pushed a commit that referenced this pull request Nov 26, 2025
(cherry picked from commit da8c4b2)
@github-actions
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
feature-layers

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

jsanz added a commit that referenced this pull request Nov 26, 2025
(cherry picked from commit da8c4b2)

Co-authored-by: Jorge Sanz <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants